Issue: #29058
PR with the breaking change: #29060

Description

This PR adds breaking change preannouncements for the PSRoleDefinition type restructuring in Az.Resources 10.0.0 / Az 16.0.0.

The breaking change involves:

• Removing flattened properties (Actions, NotActions, DataActions, NotDataActions, Condition, ConditionVersion) from PSRoleDefinition
• Replacing them with a Permissions array containing permission objects with these properties

Affected cmdlets:

Example output

PS C:\Users\atomassilli\repos\azure-powershell> pwsh -NoProfile -Command "Import-Module './artifacts/Debug/Az.Accounts/Az.Accounts.psd1' -Force; Import-Module './artifacts/Debug/Az.Resources/Az.Resources.psd1' -Force; Get-AzRoleDefinition -Name 'Reader' 2>&1"
WARNING: Upcoming breaking changes in the cmdlet 'Get-AzRoleDefinition' :
The output type PSRoleDefinition is changing. The flattened properties 'Actions', 'NotActions', 'DataActions', 'NotDataActions', 'Condition', and 'ConditionVersion' are being removed. Use 'Permissions[n].Actions', 'Permissions[n].DataActions', etc. instead to access the full permission structure with per-permission conditions.
- The change is expected to take effect in Az version : '16.0.0'
- The change is expected to take effect in Az.Resources version : '10.0.0'
Note : Go to https://aka.ms/azps-changewarnings for steps to suppress this breaking change warning, and other information on breaking changes in Azure PowerShell.

Name             : Reader
Id               : acdd72a7-3385-48ef-bd42-f606fba81ae7
IsCustom         : False
Description      : View all resources, but does not allow you to make any changes.
Actions          : {*/read}
NotActions       : {}
DataActions      : {}
NotDataActions   : {}
AssignableScopes : {/}
Condition        : 
ConditionVersion : 

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. ✅
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction - N/A (no cmdlet API change, only preannouncement attributes)
• SHOULD have proper test coverage for changes in pull request. - N/A (preannouncement only)
• SHOULD NOT adjust version of module manually in pull request ✅